| Author |
Thread Statistics | Show CCP posts - 18 post(s) |
Torgeir Hekard
Brutor Tribe
Minmatar Republic
0
   |
Posted - 2013.05.21 17:49:00 -
[1] - Quote
Launcher fails to start after update with the error "could not load python.dll"
Repair fails to start with the error "LoadLibrary(pythondll) failed" followed by error "c:\users\username\temp\nso2cc.tmp\PYTHON27.dll"
Ubuntu 12.04 x86 wine 1.4, overrides for eve.exe are msvcrt80/90/100=n,b
PS: admittedly I've never used the repairer before, so found out about the problem just now. |
Torgeir Hekard
Brutor Tribe
Minmatar Republic
0
|
Posted - 2013.05.21 20:02:00 -
[2] - Quote
Torgeir Hekard wrote:Launcher fails to start after update with the error "could not load python.dll"
UPD:
Installed PlayOnLinux. Installed wine 1.5.30 with it. Didn't bother installing EVE in PlayOnLinux and just used the updated wine version to start the repairer. On the second try it worked and corretly patched the client.
Launcher still welps with python error with wine 1.4, but works with 1.5.30. Once. Then you need to clear it's cache or get a broken window (the login part).
Launcher still tries to kill my CPU. Possibly related to this funny stuff:
it starts with fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
followed by err:ntdll:RtlpWaitForCriticalSection section 0x7bcb3ae0 "rtl.c: peb_lock" wait timed out in thread 0036, blocked by 002c, retrying (60 sec) (several different threads. About 8)
and finally ends with err:seh:setup_exception_record stack overflow 1248 bytes in thread 003e eip 7bc401ef esp 08610e50 stack 0x8610000-0x8611000-0x8710000 (again, about 8 different threads) |
Torgeir Hekard
Brutor Tribe
Minmatar Republic
0
|
Posted - 2013.05.22 02:51:00 -
[3] - Quote
Okay, seems like the dreaded Error -7 is, indeed, random and not connected with clearing the launcher cache. Which is kinda good because I don't need to clear the cache, but kinda bad, because I don't have control over it.
There is another problem, though.
The new launcher breaks the logic behind virtual desktops. That is, I can't spawn multiple instances of eve online in different virtual desktops from one launcher.
Therefore, when using launcher, to get different virtual desktops it's required to start multiple instances of launcher (with "close after game launch" option). Naturally, only one instance of launcher can be run at a time. Naturally, it can't close properly, because the threads are left in gridlock for a minute after closing the launcher. Which leads to the fact that you can only start the client once a minute. Those that hate multiboxers should probably rejoice at this point.
Why do we even need a multithreaded launcher? Does it participate in Folding @Home or something? |
Torgeir Hekard
Brutor Tribe
Minmatar Republic
0
|
Posted - 2013.05.22 03:17:00 -
[4] - Quote
Midnight Hope wrote:Doublewhopper wrote:Have to invalidate my last statement.
It worked for me once. Now i can't get the login fields and the button to appear...otherwise the launcher seems to work. Same issue here. The launcher validates everything ok, but the username/pswd and "login" button don't show up. Something is scrcewed up with the way it displays them.
It's the Error -7. It's just written in invisible letters. You can see it by selecting the text. |
Torgeir Hekard
Brutor Tribe
Minmatar Republic
0
|
Posted - 2013.05.22 04:01:00 -
[5] - Quote
Eoras Northwind wrote:I was getting similar issues with the launcher only working once and never again.
It would continually spawn these processes:
C:\Program Files\CCP\EVE\launcher\appdata\EVE_Online_Launcher-2.1.539169.win32\launcher.exe --esky-slave-proc C:\users\*your user*\Temp\esky-slave-procs\slave-37.0.txt
Each one took 2.4Gb of resident RAM, and maxed out a 2.8GHz core.
That's no moon. Errrr... That's no 3 processes. That's you using htop. If you'd sort the process tree by comand line, you'd find like 10 instances of the launcher there. Because by default htop shows userland threads. Hide them in options, and you'd get one process. |
Torgeir Hekard
Brutor Tribe
Minmatar Republic
7
|
Posted - 2013.06.14 03:37:00 -
[6] - Quote
COMM4NDER wrote:[quote=Eleriien Krhaagh]Anyhow i created two bugreports in the bugtracker for wine and if you got more information it would be apriciated or even commenting that you also have this. Please note if you tried without any infecting overrides because winedevs frown on that.
Are you sure that rendering problem is not actually SSL problem?
I've got no rendering problems since patching SSL.
As for CPU usage - this is no longer an issue for me since one of the updates. MAYBE it's related to updating wine, but not likely, since it was a launcher problem (that is, present on windows too), not wine problem, and should have been fixed as per patchnotes. |
Torgeir Hekard
Brutor Tribe
Minmatar Republic
7
|
Posted - 2013.06.14 14:09:00 -
[7] - Quote
COMM4NDER wrote:[quote=Torgeir Hekard][quote=COMM4NDER]
As for the CPU usage its still there with wine 1.6rc1
.
2 suggestions.
1) Run repair.exe. For me it reinstalled the launcher and apparently did something to it.
2) In launcher settings, set number of download threads to 1, then exit launcher, wait till the threads run out, then run it again. |
| |
|